Skip to content

Conversation

fordN
Copy link
Contributor

@fordN fordN commented Nov 18, 2024

What's changed

  • Added syncingNetwork column to the Actions table (and corresponding types and models)
  • Updated indexer-cli actions module to use syncingNetwork by adding --syncing or -s parameter to commands. --syncing can now be used to filter the following commands: actions get, actions update, actions delete, and actions approve.

Example usage

The newly support --syncing (-s) option for actions modules commands extends current functionality to provide more expressive filtering of actions commands. Here are a few examples of using it in commands:

  • graph indexer actions get --syncing arbitrum-one - Get all actions for deployments syncing data from arbitrum-one.
  • graph indexer update --network arbitrum-one --syncing mainnet status queued - Update the status for all actions for deployments syncing mainnet data on the arbitrum-one Graph Network.
  • graph indexer actions approve --network arbitrum-one --syncing base - Approve all actions on the arbitrum-one network for deployments syncing data from the base network.

- Syncing network is the network/chain that the subgraph deployment
extracts data from.
- Add -s,--syncing option to `indexer actions approve queued ...` so
user can approve actions by syncing-network.
- Add optional --network and --syncing options to `indexer actions
update ...` so user can filter the actions to be updated by protocol
network or syncing network.
- Can now supply multiple filters to `indexer actions delete`: --status,
--syncing, and --network.
@fordN fordN self-assigned this Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🚩 In Review
Development

Successfully merging this pull request may close these issues.

1 participant